docs: record confirmed product scope and planning workflow (#3) - #4

Summary

Medora now has a user-confirmed product foundation and persistent planning records, so future work can trace product choices to the original questions and replies. Agent instructions require every grilling session and unrelated follow-up to preserve context, dependencies, interpretation, and history.

.planning/
├── README.md                  recording rules and indexes
├── templates/                 session, decision and follow-up schemas
├── decisions/<time>-3/         confirmed product scope, source replies and history
└── follow-ups/<time>-<title>/  nine open records with revisit triggers

Fixes #3.

The agreed first increment is a functional practice-management platform enhanced with AI, including conversational WhatsApp booking, staff-reviewed reservations, patient profiles/intake, basic changes and immediate verified cancellations. The scope review records roles, communication contacts, language memory, handoff, collaboration, availability and honest delivery states.

The user explicitly confirmed the final summary. Detailed policies, verification/permissions, communication flows, profiles and beta gates remain focused follow-ups, alongside earlier geography/integration/translation work. No technical stack was selected and no application behavior was implemented.

Evidence

• Before: the product vision had no persistent interview or follow-up record format.
• After: source replies and revisions link to the confirmed scope and nine open follow-ups. Repository checks, Markdown links and planning metadata/dependency validation pass. D040 records the final user reply: "yes confirmed".

Merge Danger

Door: two-way

Documentation and repository agent instructions only. Follow-ups remain prerequisites to affected implementation/use.

Blast Radius: planning